System and method for robotic ticket scratching via live remote mobile interface

ABSTRACT

A controller is configured to obtain first image data from a camera associated with a ticket processing apparatus; transmit the first image data to an application server; receive, from the application server, a dispense command for the ticket processing apparatus; cause the ticket processing apparatus to dispense, based on the dispense command, a ticket having a scratching area; receive a user-provided scratching command from the application server; and cause a robotic scratching device to scratch, or remove an opaque substance from, the scratching area of the ticket in accordance with the user-provided scratching command.

RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No.17/478,907, filed Sep. 18, 2021, which claims priority to U.S.Provisional Patent Application No. 63/203,666, filed Jul. 27, 2021, eachof which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present application relates to the field of network-connectedrobotic devices configured to interact with government-regulated lotteryticket dispensing machines.

BACKGROUND

Sales of lottery tickets (also referred to as scratch tickets orscratchers) are typically regulated by state or other governmentalagencies, which require that tickets be sold at physical locations(e.g., points of sale) within their jurisdictions. As such, those whowish to participate in a preferred lottery game but cannot be present atone of these physical locations (e.g., due to a vacation, disability, orlack of convenient store location) may be prevented or discouraged frompurchasing desired lottery tickets. Due to the nature of the lottery,many players prefer to purchase the same tickets and play the samenumbers every lottery cycle, so the prospect of missing a particularlottery cycle can be disappointing.

In addition, lottery scratch tickets typically require physical actionsas part of the gameplay. In some instances, tickets must be scratchedoff in order to reveal underlying information (e.g., numbers, shapes,patterns, and so forth) that is required to determine whether the ticketis a winner, and if so, what the prize for that ticket is. As a result,those with circumstances that make it difficult to physically play(e.g., due to a condition making it difficult to scratch the ticket) maybe discouraged from playing.

Lastly, lottery scratch tickets may be split among a group of players(e.g., family members, coworkers, and so forth) in order to share thecost of purchasing multiple tickets (“lottery pools” or “office pools”),thereby increasing the odds of winning. In such instances, one persontypically collects the money, purchases the tickets, plays the tickets,and reports the results back to the others. As such, the others in thegroup often do not get to share in the gameplay experience and may beless likely to continue to contribute to future group ticket purchases.

SUMMARY

This disclosure describes a system and method of using a roboticapparatus that enables virtual playing of a lottery game while complyingwith governmental regulations. Players who are not physically present ata point of sale (e.g., at a remote location), or who are physicallypresent at a point of sale but who are unable to physically play theticket, can participate in a desired lottery game. The presentlydescribed system and method allow such users to participate in thelottery in each of the aforementioned scenarios in a way that providesan equivalent level of engagement and complies with applicable state,local, federal, municipal, and/or international rules of game play(e.g., regarding location, signatures, audits, and so forth).

In one aspect, a system, method, and apparatus for robotic ticketscratching via a live remote mobile interface is disclosed. The userinterface runs on an application on a mobile device, tablet, computer,or web browser. A user can be physically present in a remote location(such as a remote location within a particular state, or aninternational location). In some implementations, the user is notlocated remotely, but physically present (such as in a bingo hall) andcould use the service for convenience or due to physical limitations.

In some implementations, ticket dispensing machines are loaded withrolls of tickets or loaded individually depending form factor of ticketsacquired. There are one or more ticket dispensing machines in a setup.In some implementations, the machines are in a secure room. In someimplementations, the machines are in retail or other public locations.

In some implementations, there is a live video feed of dispensers. Usingthe user interface, a user selects the desired ticket (and dispenser ifthe same ticket is available in multiple dispensers). A ticket isadvanced from the dispenser.

In some implementations, cameras are located from multiple live angles,including top and bottom. As the ticket advances, the bottom cameraimages the ticket and a scanner scans the lot/serial number of theticket. The controller sends that information to the application server.That ticket is assigned to the user by application server to thespecific user. In some implementations, the user can remotely controlthe pan, tilt, and zoom of the one or more cameras.

In some implementations, the user can opt to sign the ticket using themobile interface. The user inputs their signature using a touchscreen,computer mouse, stylus, digital pen, keyboard, or other input methodcapturing the X-Y signature (a digital facsimile of the signature).

In some implementations, the signature file is sent from the mobileapplication to the application server to the controller to a robotic armthat physically signs the ticket. The user can view the signature beingrendered on the ticket in real time. In some implementations, thesignature feedback is replicated on the user interface.

In some implementations, the user virtually scratches the ticket fromthe remote location using the touchscreen, mouse, stylus, digital pen,or other user input. In some implementations, the scratching of theticket may be fully automated, requiring no interaction by the user(other than to begin and/or stop). In some implementations, the systemcan use random x-y coordinates.

In some implementations, as the user is scratching and watching the livevideo feed, the robotic arm is physically scratching, buffing, or bysome other means remotely revealing the ticket. In some embodiments,there is a simulated ticket on the mobile device (with or without thevideo feed) and real-time feedback is provided to digitally simulate theticket scratching on the mobile device. In some implementations, two ormore people can be watching the same feed and/or virtual scratching. Insome implementations, there can be guest watcher(s) that have noknowledge of the user or interest in the ticket.

In some implementations, upon completion of scratching, the barcodescanner scans the unique code that is revealed. In some implementations,the unique code is on the back side of the ticket. In someimplementations, the unique code does not need to be revealed. In someimplementations, the code is in a fixed spot and user interaction is notrequired to scratch the code.

In some implementations, the unique code is sent by the scanner to theticket redemption terminal to the ticket agency's validation serverwhich validates the ticket. The ticket status is returned. If the ticketis a winner, the application server sends the information includingamount to the mobile application. The mobile application then canprovide a visual, audible, and/or tactile alert to the user. The winningfunds may be deposited into the user account. The user account can belinked to a bank or card account. In some implementations, the funds maybe transferred to a virtual currency account (such as bitcoin).

In some implementations, back at the robotic machine, there is a ticketcutter that cuts the latest ticket from the stream of tickets. In someimplementations, there is a ticket sorter that ejects or separates thewinning tickets from the losing tickets. In some implementations, therecan be a pile of error tickets as well in cases where there was a systemerror, incomplete scan, or incomplete scratch.

In some implementations, each transaction (scanning, signing, and/orscratching of the ticket) may be video logged and stored for laterrecall and authentication verification based on auditing and/orgoverning requirements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram of a network-connected lottery system 100 inaccordance with some implementations.

FIG. 2 is a schematic diagram of the network-connected lottery system100 of FIG. 1 including data flows in accordance with someimplementations.

FIG. 3 is a flow diagram of a method of operating a ticket processingsystem of the lottery system 100 of FIGS. 1 and 2 in accordance withsome implementations.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DETAILED DESCRIPTION

In the era of mobile devices and connectivity, playing lottery gamesvirtually can be accomplished using a robotic apparatus that is presentwithin the governing jurisdiction, and a live remote mobile interfaceassociated with the player. Examples of such a robotic apparatus, mobileinterface, and methods of use thereof, are described herein.

FIG. 1 is a system diagram of a network-connected lottery system 100 inaccordance with some implementations, and FIG. 2 is a schematic diagramof the network-connected lottery system 100 of FIG. 1 including moredetailed data flows in accordance with some implementations.

As depicted in FIGS. 1 and 2 , the lottery system 100 includes a ticketprocessing system 102, which is physically located in the jurisdictionthat governs the lottery that is administered by the lottery system 100.

The ticket processing system 102 includes a ticket dispensing machine190, a redemption terminal 120, a controller 110, a scanning device(scanner) 118, one or more video cameras 112, and a plurality of roboticcomponents including a robotic signature mechanism (signer) 114, arobotic scratching mechanism (scratcher) 116, a cutting device (cutter)132, and/or a sorting device (sorter) 134.

The ticket processing system 102 may be located in a public location(e.g., a retail or other public location), or in a private location,such as a secure room that is designed to house the various componentsof the processing system 102.

The ticket processing system 102, or components included in the ticketprocessing system 102, may be referred to as a robotic machine orapparatus. In some implementations, the components forming the roboticmachine or apparatus include the controller 110, the signer 114, thescratcher 116, the cutter 132, the sorter 134, and hardware forreceiving, moving, orienting, or otherwise handling tickets dispensedfrom the dispensing machine 190 in order to ensure proper imaging,scanning, signing, scratching, and processing of each ticket dispensedfrom the dispensing machine 190.

The ticket dispensing machine 190 includes a plurality of lotterytickets 192 (e.g., loaded with rolls 192 of tickets or loadedindividually depending on the form factor of the tickets). There may beone or more ticket dispensing machines 190 in a single processing system102.

The dispensing machine 190 is configured to receive a dispense commandfrom the controller 110 and output a ticket specified by the dispensecommand (if there are multiple types of tickets within the dispensingmachine 190), or output a ticket in accordance with receiving thedispense command regardless of whether the dispense command specifies aparticular type of ticket (e.g., if there is only one type of ticketwithin the dispensing machine 190). The dispense command may include aquantity of tickets to dispense. In such a scenario, the dispensingmachine 190 is configured to dispense the number of tickets specified bythe dispense command, one at a time, so that the other components of theprocessing system 102 may process each ticket in the manner describedbelow.

In some implementations, other components of the processing system 102(e.g., the signer 114, scratcher 116, camera(s) 112, and/or scanner 118)may be disposed within the dispensing machine 190. Alternatively, thedispensing machine 190 may be a machine that is modified to acceptdispense commands from the controller 110 in place of, or in additionto, dispense commands triggered by physical gameplay on the dispensingmachine 190 itself (e.g., entering money, pressing selection buttons,and so forth). In such scenarios, the other components of the processingsystem 102 may be located outside of and in proximity to the dispensingmachine 190 in order to process tickets outputted by the dispensingmachine 190.

The tickets included in the dispensing machine 190 (e.g., arranged in aticket roll 192 or any other arrangement) may also be referred to asscratch cards, scratch offs, scratch tickets, scratchers, scratch-its,scratch games, scratch-and-wins, instant games, or instant lotteries.The tickets may be constructed of thin paper-based card material orplastic. One or more areas may contain concealed information which canbe revealed by scratching off an opaque substance (e.g., a silkscreenlatex panel that bonds with the ticket body), or removing an adhesive.The opaque substance may also be referred to as a coating, panel, label,scratch coating, scratch panel, scratch label, scratch substance, orscratching area.

In some implementations, the entire scratchable area (or at least athreshold of the scratchable area) needs to be scratched to see whethera prize has been won. The ticket may be printed either to be a winner ornot, or to reveal a secret code. In some implementations, the resultdoes not depend upon the portions that are scratched off. In otherimplementations, some but not all areas have to be scratched; this mayapply in a quiz, where the area corresponding to the right answer isscratched, or in some applications where, depending on which areas arescratched, the card wins or loses. In these cases the card becomesinvalid if too many areas are scratched. After losing, one can scratchall areas to see if, how, and what one could have won with this ticket.

The video camera(s) 112 may be located at multiple locations within theticket processing system 102, providing multiple live angles. Forexample, a first camera 112 may include the ticket dispensing machine(s)190 in its field of view, a second camera 112 may include the top of adispensed ticket 196 in its field of view, and a third camera 112 mayinclude the bottom of a dispensed ticket 196 in its field of view. Assuch, users of the lottery system 100 may remotely view (i) thedispensing machine(s) 190 in order to determine which machine and/orticket to select, (ii) the top of a dispensed ticket 196 in order toview a scratching area, and/or (iii) the bottom of a dispensed ticket196 in order to view a signing area.

In some implementations, users can remotely control the pan, tilt, andzoom of the camera(s) 112. Optionally, two or more users can be watchingthe same video feed provided by the camera(s) 112 during a single ticketplaying session (e.g., viewing virtual scratching as described below).In some implementations, there may be guest watchers that have noknowledge of the user or interest in the ticket being dispensed andscratched.

The scanner 118 is located proximate to an area in which dispensedtickets 196 are provided, and configured to scan identifying informationon dispensed tickets 196. For example, identifying information for aticket may include a unique code such as a lot number or serial numberthat identifies the ticket. Such a code may or may not be hidden behindthe opaque substance. The scanner 118 is configured to transmit theidentifying information (either the scan of the identifying information,or the identifying information itself) to the controller 110.

In some implementations, the scanner 118 is further configured to scaninformation (e.g., numbers, letters, symbols, markings, and so forth)that is hidden behind the opaque substance and revealed upon the ticketbeing scratched. The scanner 118 is configured to transmit suchinformation (either the scan of the information, or the informationitself) to the redemption terminal 120.

The ticket redemption terminal 120 either includes the scanner 118 or iscoupled to the scanner 118, and is configured to receive data obtainedby the scanner 118. Depending on the nature of the scanned data, theticket redemption terminal 120 may transmit the scanned data (orinformation, such as a number, derived from the scanned data) to thecontroller 110 or the ticket validation server 122.

In a first example, the ticket redemption terminal 120 may send ascanned identification number (e.g., a serial number) of a dispensedticket 196 to the controller 110, so that the controller 110 may linkthe ticket associated with the scanned identification number to a useraccount associated with a user currently playing that ticket (e.g., viauser device 104 and application 105, application server 108, andcontroller 110).

In a second example, the ticket redemption terminal 120 may send scanneddata associated with the game play of the ticket (e.g., a code revealedfrom under the opaque substance) to the ticket validation server 122 forvalidation by the ticket agency 124 (e.g., in order to validate that theticket is a winner or not a winner). In some implementations, the dataassociated with the game play may be the identification number (e.g.,the serial number). In other words, a single number may not onlyidentify the ticket (and be linked to a user account by the applicationserver 108), but also serve as the basis for validating whether theticket is a winning ticket or not a winning ticket. In such scenarios,the ticket may not even need to be played (e.g., may not need to bescratched), and scanning a single number on a dispensed ticket 196 maybe adequate in order to (i) link the ticket to a user account, and (ii)validate the status of the ticket (e.g., winner or loser).

The ticket redemption terminal 120 is configured to receive the ticketvalidation information (e.g., win/loss information) from the ticketvalidation server 122 and transmit the ticket validation information tothe application server 108 for further processing.

The controller 110 comprises at least one processor (also referred to asa processing unit, processor, computer, programmable apparatus, or anyelectronic technology capable of executing instructions or operations).The controller 110 comprises or is communicatively coupled to memorystoring one or more programs to be executed by the processing unit(s) ofthe controller. The memory includes computer readable media including,but not limited to, attached storage media (e.g., hard disk drives,network disk drives, servers), internal storage media (e.g., RAM, ROM,EPROM, FLASH-EPROM, or any other memory chip or cartridge), removablestorage media (e.g., CDs, DVDs, flash drives, memory cards, floppydisks, flexible disks), firmware, and/or other known or yet to bediscovered storage media. Depending on its purpose, the memory may betransitory and/or non-transitory.

The controller 110 is configured to receive dispense commands from theapplication server 108 and transmit received dispense commands to thedispensing machine 190. The controller 110 is also configured to receivevideo data from one or more cameras 112 and transmit the video data tothe application server 108. The controller 110 is also configured toreceive signing data and scratch data (described in more detail below)from the application server 108 and transmit the signing data andscratch data to the signer 114 and the scratch 116, respectively. Thecontroller 110 is also configured to receive scan data (e.g., serialnumbers and/or gameplay data as described above) from the scanner 118,and transmit the scan data to the application server 108 for linking toa user account 106.

In some implementations, the controller 110 may be configured to receivewin/loss information from the redemption terminal 120 and transmit thewin/loss information to the application server 108. Alternatively, theredemption terminal 120 (or the ticket validation server 122) maytransmit the win/loss information to the application server 108 withoutgoing through the controller 110.

The signer 114 is a mechanical device that is configured to manipulate awriting tool (e.g., a pen, marker, or other signing tool) to sign thesigning area of a ticket in accordance with signing data received from auser device 104 via the application server 108 and the controller 110.The signer 114 may also be referred to as a signing or signature device,signing or signature mechanism, signing or signature machine, automaticsigner, or automatic pen. For example, the signer 114 may be a roboticarm.

The signer 114 may be controlled remotely by the user interface of anapplication 105 of a user device 104. The user may virtually (remotely)control the signer 114 to sign the dispensed ticket 196 by locallysigning a user interface element resembling the signing area of theticket on the application 105 of the user device 104. For example, theuser may use a touchscreen, computer mouse, stylus, digital pen,keyboard, or other input method of the user device 104, thereby causingthe application 105 to capture X-Y signature data (with the X and Y axesrepresenting horizontal and vertical directions on a face of theticket). In some implementations, the X-Y signature data corresponds totwo-dimensional user-provided gestures corresponding to signature inputat the user device. In some implementations, the user may view thesignature being rendered on the ticket in real time, with signaturefeedback being replicated (displayed) on the user interface of theapplication 105.

The scratcher 116 is a mechanical device that is configured tomanipulate a scratching tool (e.g., a needle, scratching tool, or otherhard object) to scratch the opaque substance off of the scratching areaof the ticket in accordance with scratching data received from a userdevice 104 via the application server 108 and the controller 110. Thescratcher 116 may also be referred to as a scratching device, scratchingmechanism, scratching machine, or automatic scratcher. For example, thescratcher 116 may be a robotic arm that physically scratches the ticket.

In some implementations, the scratcher 116 and the signer 114 may sharesome components. For example, a single robotic arm may be used to (i)sign the signing area of the ticket when configured in a signing mode(e.g., with a signing tool inserted at a moving end of the arm) and (ii)scratch the scratching area of the ticket when configured in ascratching mode (e.g., with a scratching tool inserted at the moving endof the arm). While the robotic arm is configured in one mode, the toolassociated with the other mode may be retracted from the moving end ofthe arm.

In some implementations, the scratcher 116 and the signer 114 may beindependently constructed and operated, such as for cases in which thescratching area is on one side of the ticket and the signing area is onthe other side of the ticket. Alternatively, for such a ticketconfiguration, a ticket flipping mechanism may reorient the ticket sothat a single robotic arm may both sign and scratch the ticket asdescribed above.

The scratcher 116 may be controlled remotely by the user interface of anapplication 105 of a user device 104. The user may virtually (remotely)control the scratch 116 to scratch (or remove an opaque substance from)a scratching area of the dispensed ticket 196 by locally interactingwith a user interface element resembling the scratching area of theticket on the application 105 of the user device 104. For example, theuser may use a touchscreen (e.g., by using swiping gestures), computermouse, stylus, digital pen, keyboard, or other input method of the userdevice 104, thereby causing the application 105 to capture scratchingdata. In some implementations, the scratching data captured at theapplication 105 is X-Y scratching data (with the X and Y axesrepresenting horizontal and vertical directions on a face of theticket), corresponding to two-dimensional user-provided gesturescorresponding to scratching input at the user device. Alternatively, thescratching data captured at the application 105 may include or comprisea command instructing the scratcher 116 to scratch (or remove an opaquesubstance from) a scratching area of the dispensed ticket, using ascratching pattern that is independent of any user-provided gestures.For example, the user may select a “scratch ticket” affordance on theuser interface of the application 105, causing a scratch command to besent to the scratcher 116. The scratcher 116 may receive the scratchcommand and use a preconfigured scratching pattern or a randomscratching pattern to scratch (or remove an opaque substance from) thescratching area of the dispensed ticket.

In some implementations, the user may view the scratching on thedispensed ticket 196 in real time, with scratching feedback beingreplicated (displayed) on the user interface of the application 105. Thescratching feedback may be a digital simulation of a ticket beingscratched on the user interface, and/or live video feed of the dispensedticket 196 being scratched by the scratcher 116.

In some implementations, rather than manually interacting with ascratching element of the user interface of the application 105, thescratching of the dispensed ticket 196 may be fully automated, requiringno interaction by the user, other than to begin and/or stop scratching(e.g., controlled by one or more affordances on the user interface).

The ticket cutter 132 (also referred to as a cutting device or cuttingmechanism) is a mechanical device including a cutting element configuredto separate dispensed tickets 196 from tickets in the stream 194 thathave not yet been dispensed or otherwise processed. The ticket cutter132 receives a cut command from the controller 110 after the ticket 196has been processed (e.g., after the ticket has been signed, scratched,and scanned).

The ticket sorter 134 (also referred to as a sorting device or sortingmechanism) is a mechanical device including a sorting element configuredto eject or separate the winning tickets from the losing tickets. Theticket sorter 134 receives a sort command from the controller 110 afterthe ticket 196 has been processed (e.g., after the ticket has beensigned, scratched, and scanned). The ticket sorter 134 may place thewinning tickets into a winning ticket pile or receptacle 138 and thelosing tickets into a losing ticket pile or receptacle 136, making themavailable for system auditing and, in some cases, physical proof ofwinning tickets that may be sent (e.g., mailed or otherwise delivered)to the ticket agency 124 and/or the user who purchased and/or played theticket. In some implementations, in the event of a system error, anincomplete scan, or an incomplete scratch, the ticket sorter 134 mayplace tickets corresponding to such errors into an error ticket pile orreceptacle (not shown), making them available for systemtroubleshooting.

The application server 108 comprises at least one processor (alsoreferred to as a processing unit, processor, computer, programmableapparatus, or any electronic technology capable of executinginstructions or operations). The application server 108 comprises or iscommunicatively coupled to memory storing one or more programs to beexecuted by the processing unit(s) of the controller. The memoryincludes computer readable media including, but not limited to, attachedstorage media (e.g., hard disk drives, network disk drives, servers),internal storage media (e.g., RAM, ROM, EPROM, FLASH-EPROM, or any othermemory chip or cartridge), removable storage media (e.g., CDs, DVDs,flash drives, memory cards, floppy disks, flexible disks), firmware,and/or other known or yet to be discovered storage media. Depending onits purpose, the memory may be transitory and/or non-transitory.

The application server 108 is configured to receive commands (e.g.,system 102 selection commands, machine 190 selection commands, and/orticket dispense commands) and data (e.g., signing and scratching data)from a plurality of user devices 104 (with one representative devicebeing depicted in FIGS. 1 and 2 ) and transmit the commands and data toa plurality of ticket processing systems 102 (with one representativesystem 102 being depicted in FIG. 2 ). The application server 108 isalso configured to receive commands and data (e.g., scan data and/orvideo data) from the plurality of user devices 104 and transmit thecommands and data to the plurality of user devices 104.

In some implementations, the application server 108 is also configuredto receives win/loss (ticket status) information from the redemptionterminal 120 or from the controller 110, and transmit notifications tothe user device 104 communicating the win/loss information.

In some implementations, the application server 108 is also configuredto assign or link dispensed tickets 196 (based on or associated withreceived scan data, such as ticket serial numbers) to user accounts 106corresponding to users who caused the tickets to be dispensed.

The user device 104 is an electronic communication device, such as amobile device, tablet, computer, or web browser. Using one or moreprocessors, the user device 104 executes a remote lottery application105, which runs a user interface configured to provide outputs to theuser (e.g., video feed(s) from the application server 108, menusproviding options for selection dispensing machines and tickets, userinterface affordances for accepting dispense commands, winning ticketnotifications, and so forth). The user interface also accepts userinputs configured to operate the signer 114 and scratcher 116 asdescribed above.

Using the application 105, a user can be physically present in a remotelocation while playing a lottery ticket offered by the ticket processingsystem 102. In some implementations, the user may not be locatedremotely, but may be physically present (such as in a bingo hall) at thelocation of the ticket processing system 102, optionally using theapplication 105 for convenience or due to physical limitations.

The application 105 displays video feed data (from the camera(s) 112)and receives selections for desired tickets and/or dispensing machines(if the same ticket is available in multiple dispensing machines). Theapplication 105 receives inputs via an input module of the user device104. The input module may comprise a touchscreen, computer mouse,stylus, digital pen, keyboard, or other input device capturing X-Ymovements (e.g., for signing and/or scratching).

The application 105 receives win/loss information (including winningamounts) from the application server 108. The application 105 may causethe user device 104 to alert the user regarding the win/loss informationusing a visual, audible, and/or tactile alert.

The ticket agency 124 is associated with the tickets and/or ticketdispensing machines 190 offering the tickets. The ticket agency, throughits ticket validation server 122, validates tickets and their win/lossstatuses. Upon a ticket being confirmed to be a valid, winning ticket(by the ticket validation server 122) the ticket agency 124 depositswinning funds into the user account 106 linked to the ticket by thescanned identification number (e.g., serial number, as described above).The ticket agency 124 may deposit funds to the user via a provider bankaccount 126 and payment processing module or service 128. The useraccount 106 may be linked to a bank or card account 130. In someimplementations, funds may be transferred to a virtual currency account(such as bitcoin) associated with the user account.

In some implementations, system 100 may include additional components,or only a subset of the components described above. For example, someimplementations of system 100 may not include the ticket agency 124,ticket validation server 122, provider bank account 126, paymentprocessing module 128, and/or user bank/card account 130. Instead,system 100 may be configured to communicate with one or more of thesecomponents.

In some implementations, one or more of the components of system 100 maybe combined (i.e., operations for two or more components may be executedby a single server, device, controller, etc.). For example, the ticketvalidation server 122 and redemption terminal 120 may combined, theredemption terminal 120 and the controller 110 may be combined, and soforth.

In some implementations, one or more of the components of ticketprocessing system 102 may be implemented as a robotic machine. Forexample, a machine may be controlled by controller 110 and include thesigner 114, scratcher 116, scanner 118, camera(s) 112, redemptionterminal 120, cutter 132, sorter 134, and/or dispensing machine 190.

The ticket processing system 102 (specifically, the controller 110 andthe redemption terminal 120) communicate with the other components ofsystem 100 over one or more communication network connections (denotedby arrows in the figures). The communication network connections may bewired or wireless communications connections that are ongoing (e.g.,dedicated connections, dedicated online connection, and/or hardwiredconnections) or accessible on demand (e.g., supporting the ability forthe machine to make a temporary connection to a server or the abilityfor the user device to contact a server). Examples of such networkconnection technology may include hardwired, telephone networktechnology, cellular technology (e.g., GSM, CDMA, or the like), Wi-Fitechnology, wide area network (WAN), local area network (LAN), or anywired or wireless communication technology over the Internet that isknown or yet to be discovered. Stated another way, each communicationnetwork connection may be implemented over a communication network usinga wired or wireless communication protocol (e.g., any of WiFi,Bluetooth, ZigBee, Z-Wave, 6LoWPAN, Thread, 4G, 5G, and the like).

Communications within the ticket processing system 102 (denoted byarrows in the figures) may take place using the communicationtechnologies described above. Additionally or alternatively, suchcommunications may take place using short-range communicationtechnology, such as Bluetooth (such as Bluetooth 4.0, Bluetooth Smart,Bluetooth Low Energy (BLE)), near-field communication (NFC), UltraWideband (UWB), radio frequency identification (RFID), infraredwireless, induction wireless, or any wired or wireless technology thatcould be used to communicate a small distance (approximately a hundredfeet or closer) that is known or yet to be discovered.

FIG. 3 is a flow diagram of a method of operating a ticket processingsystem of the lottery system 100 of FIGS. 1 and 2 in accordance withsome implementations. Method 300 is, optionally, governed byinstructions that are stored in computer memories or non-transitorycomputer readable storage mediums of processing system 102, applicationserver 108, redemption terminal 120, and/or validation server 122. Suchinstructions may be executed by one or more processors of theaforementioned devices. The computer readable storage mediums mayinclude magnetic or optical disk storage devices, solid state storagedevices such as Flash memory, or other non-volatile memory devices. Theinstructions stored on each computer readable storage medium may includeone or more of: source code, assembly language code, object code, orother instruction formats that are interpreted by one or moreprocessors. Some operations in method 300 may be combined and/or theorder of some operations may be changed.

Method 300 may begin with operation 302 or 304. At operation 302, thecontroller 110 obtains, from one or more video cameras 112 in proximityto a ticket dispensing machine 190, a first video stream (showing a livefeed of the dispensing machine), and transmits the first video stream toan application server 108 for delivery to a user device 104.

Using the user interface of an application 105 running on the userdevice 104, a user selects a desired ticket and/or dispensing machine190, optionally based on the first video stream (e.g., the user viewsthe available tickets and/or dispensing machines in the video feed andmakes a selection in the user interface).

Upon receiving the user selection, the user device transmits a dispensecommand to the controller 110 via the application server 108, where itis received at operation 304. Upon receiving the dispense command, thecontroller 110 causes the selected dispensing machine to dispense theselected ticket. The dispensed ticket is a physical lottery ticket thathas a scratching area, a signature area, and/or an identification code(e.g., a lot number or serial number) that is either viewable upon beingdispensed, or must be revealed by a scratcher.

As the ticket advances, a first camera 112 (e.g., a bottom camera)images the ticket and a scanner 118 scans the identification code(operation 306) of the ticket. The controller 110 transmits the scannedidentification number (referred to as first ticket data) to theapplication server 108. In operation 308, the application server 108links (i.e., assigns, associates) the identification code of the ticketto a user account 106 associated with the user device 104.

Before, during, or after operation 306, the controller 110 receivesuser-provided signing data (operation 310) and/or user-providedscratching data (operation 314) from the application server 108(obtained by the user device 104). The signing data causes a roboticsignature device to sign the signature area of the ticket (operation312), and/or the scratching data causes a robotic scratching device toscratch the scratching area of the ticket (operation 316).

In other words, the user can opt to sign the ticket (operation 310)using the user interface of the application 105. The user inputs asignature using a touchscreen, computer mouse, stylus, digital pen,keyboard, or other input method capturing the X-Y Signature. Thesignature file is sent from the mobile application to the applicationserver to the controller to a robotic arm that physically signs theticket (operation 312). The user can view the signature being renderedon the ticket in real time. In some implementations, the signaturefeedback is replicated on the user interface.

Before, during, or after the signing operation, the user may virtuallyscratch the ticket (operation 314) using the touchscreen, mouse, stylus,digital pen, or other user input. In some implementations, thescratching of the ticket may be fully automated, requiring nointeraction by the user (other than to begin and/or stop). In someimplementations, the scratching device can use random x-y coordinates.As the user performs scratching gestures on the user interface and/orwatches the live video feed, the robotic arm physically scratches theticket. In some implementations, there is a simulated ticket on the userdevice 104 (with or without the video feed) and real-time feedback isprovided to digitally simulate the ticket scratching on the user device104.

Upon completion of the scratching operation, the scanner 118 scans(operation 318) information that is revealed in the scratching area(referred to as second ticket data). The information may include aunique code, gameplay numbers, or any other data initially hiddenunderneath the opaque substance before the scratching operation. In someimplementations, the information does not need to be revealed. In someimplementations, the information is in a fixed spot and/or a scratchingoperation is not required. The scanner 118 transmits the second ticketdata (the revealed information) to the ticket redemption terminal 120for processing by the ticket validation server 122 (or is sent directlyto the ticket validation server 122).

Upon receiving the second ticket data, the ticket agency (by way of thevalidation server 122) determines ticket status data corresponding to awin status or a loss status of the ticket based on the second ticketdata in operation 320. If the ticket is a winning ticket (the ticketstatus data corresponding to a win status), the validation server 122transmits a notification to the application server 108 (for delivery tothe user device)) including an amount associated with the win status ofthe ticket in operation 322.

The application server 108 updates the user account based on thewin/loss status, and notifies the user device accordingly (operation324). Funds corresponding to the amount associated with the win statusmay be automatically transferred to a bank account linked to the useraccount associated with the user device (e.g., by the ticket agencyusing a payment processing service 128).

In some implementations, after the ticket is processed (upon completionof operations 312, 316, and 318), the controller 110 may cause a cuttingdevice 132 to cut or otherwise separate the processed ticket from astream of tickets. The controller 110 may further cause a sorting device134 to ejects or separate the winning tickets from the losing tickets,thereby storing the processed ticket in accordance with win or lossstatus. In some embodiments, there may be a pile of error tickets incases where there was a system error, an incomplete scan, or incompletescratch.

In some implementations, each ticket processing transaction (e.g.,operations 302-318 at the processing system 102) may be video logged andstored (e.g., at the controller 110 and/or the application server 108)for later recall and authentication verification, thereby satisfyingauditing and/or governing requirements.

It will be appreciated by those skilled in the art that changes could bemade to the exemplary embodiments shown and described above withoutdeparting from the broad inventive concept thereof. It is understood,therefore, that this invention is not limited to the exemplaryembodiments shown and described, but it is intended to covermodifications within the spirit and scope of the present invention asdefined by the claims.

For example, specific features of the exemplary embodiments may or maynot be part of the claimed invention, different components as opposed tothose specifically mentioned may perform at least some of the featuresdescribed herein, and features of the disclosed embodiments may becombined.

As used herein, the terms “about” and “approximately” may refer to + or−10% of the value referenced. For example, “about 9” is understood toencompass 8.2 and 9.9.

It is to be understood that at least some of the figures anddescriptions of the invention have been simplified to focus on elementsthat are relevant for a clear understanding of the invention, whileeliminating, for purposes of clarity, other elements that those ofordinary skill in the art will appreciate may also comprise a portion ofthe invention. However, because such elements are well known in the art,and because they do not necessarily facilitate a better understanding ofthe invention, a description of such elements is not provided herein.

It will be understood that, although the terms “first,” “second,” etc.are sometimes used herein to describe various elements, these elementsshould not be limited by these terms. These terms are only used todistinguish one element from another.

For example, a first element could be termed a second element, and,similarly, a second element could be termed a first element, withoutchanging the meaning of the description, so long as all occurrences ofthe “first element” are renamed consistently and all occurrences of thesecond element are renamed consistently. The first element and thesecond element are both elements, but they are not the same element.

As used herein, the term “if” may be, optionally, construed to mean“upon” or “in response to determining” or “in response to detecting” or“in accordance with a determination that,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event]” or “in accordance with a determination that [astated condition or event] is detected,” depending on the context.

The terminology used herein is for the purpose of describing particularimplementations only and is not intended to be limiting of the claims.

As used in the description of the implementations and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise.

It will also be understood that the term “and/or” as used herein refersto and encompasses any and all possible combinations of one or more ofthe associated listed items.

It will be further understood that the terms “comprises” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,integers, operations, elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in accordance with a determination”or “in response to detecting,” that a stated condition precedent istrue, depending on the context.

Similarly, the phrase “if it is determined (that a stated conditionprecedent is true)” or “if (a stated condition precedent is true)” or“when (a stated condition precedent is true)” may be construed to mean“upon determining” or “in response to determining” or “in accordancewith a determination” or “upon detecting” or “in response to detecting”that the stated condition precedent is true, depending on the context.

Further, to the extent that the method does not rely on the particularorder of steps set forth herein, the particular order of the stepsshould not be construed as limitation on the claims. The claims directedto the method of the present invention should not be limited to theperformance of their steps in the order written, and one skilled in theart can readily appreciate that the steps may be varied and still remainwithin the spirit and scope of the present invention.

1. A system comprising one or more controllers configured to: obtainfirst image data from a camera associated with a ticket machine;transmit the first image data to an application server; receive, fromthe application server, a dispense command for the ticket machine; causethe ticket machine to dispense, based on the dispense command, a tickethaving a scratching area; receive a user-provided scratching commandfrom the application server; and cause a robotic scratching device toscratch, or remove an opaque substance from, the scratching area of theticket in accordance with the user-provided scratching command.
 2. Thesystem of claim 1, wherein the one or more controllers are furtherconfigured to: receive user-provided signing data from the applicationserver; and cause a robotic signature device to sign a signature area ofthe ticket in accordance with the user-provided signing data.
 3. Thesystem of claim 1, wherein the one or more controllers are furtherconfigured to: obtain, from a scanning device associated with the ticketmachine, an identification code of the ticket; and transmit theidentification code to a ticket validation server.
 4. The system ofclaim 1, further comprising a ticket validation server configured to:determine ticket status data corresponding to a win status or a lossstatus of the ticket based on an identification code of the ticket; andin accordance with the ticket status data corresponding to a win statusof the ticket: transmit a notification to a user device including anamount associated with the win status of the ticket; and cause fundscorresponding to the amount associated with the win status to betransferred to a bank account linked to a user account associated withthe user device.
 5. The system of claim 1, wherein the one or morecontrollers are further configured to: cause a cutting device toseparate the ticket from a stream of tickets; and cause a sorting deviceto store the ticket in accordance with a win status or a loss status ofthe ticket.
 6. The system of claim 1, further comprising an applicationserver configured to: obtain, from a scanning device, an identificationcode of the ticket; and link the identification code with a user accountassociated with a user device.
 7. The system of claim 1, wherein thefirst image data includes an image of the ticket machine and/or an imageof the ticket.
 8. The system of claim 2, wherein the ticket comprises aphysical ticket body having two surfaces, the scratching area includesan opaque substance bonded to one of the two surfaces, and the signaturearea includes a blank portion of one of the two surfaces.
 9. The systemof claim 2, wherein the user-provided signing data includes X-Y dataobtained from a user interface of a user device, wherein the X-Y datacorresponds to two-dimensional user-provided gestures corresponding tosignature input at the user interface.
 10. The system of claim 1,wherein: the user-provided scratching command causes the roboticscratching device to begin scratching, or removing the opaque substancefrom, the scratching area of the ticket; and the robotic scratchingdevice is configured to scratch, or remove the opaque substance from,the scratching area of the ticket using a preconfigured or randomscratching pattern.
 11. The system of claim 2, wherein the one or morecontrollers are further configured to obtain, from a second cameraassociated with the ticket machine, second image data including an imageof the signature area of the ticket while the robotic signature devicesigns the signature area.
 12. The system of claim 1, wherein the one ormore controllers are further configured to obtain, from a second cameraassociated with the ticket machine, second image data including an imageof the scratching area of the ticket while the robotic scratching devicescratches the scratching area.
 13. A method, comprising: at a ticketprocessing system: obtaining first image data from a camera associatedwith a ticket machine; transmitting the first image data to anapplication server; receiving, from the application server, a dispensecommand for the ticket machine; causing the ticket machine to dispense,based on the dispense command, a ticket having a scratching area;receiving a user-provided scratching command from the applicationserver; and causing a robotic scratching device to scratch, or remove anopaque substance from, the scratching area of the ticket in accordancewith the user-provided scratching command.
 14. The method of claim 13,further comprising: at the ticket processing system: receivinguser-provided signing data from the application server; and causing arobotic signature device to sign a signature area of the ticket inaccordance with the user-provided signing data.
 15. The method of claim13, further comprising: at the ticket processing system: obtaining, froma scanning device associated with the ticket machine, an identificationcode of the ticket; and transmitting the identification code to a ticketvalidation server.
 16. The method of claim 13, further comprising: at aticket validation server: determining ticket status data correspondingto a win status or a loss status of the ticket based on anidentification code of the ticket; and in accordance with the ticketstatus data corresponding to a win status of the ticket: transmitting anotification to a user device including an amount associated with thewin status of the ticket; and causing funds corresponding to the amountassociated with the win status to be transferred to a bank accountlinked to a user account associated with the user device.
 17. Anon-transitory computer readable storage medium storing one or moreprograms configured for execution by a computer system, the one or moreprograms including instructions for: obtaining first image data from acamera associated with a ticket machine; transmitting the first imagedata to an application server; receiving, from the application server, adispense command for the ticket machine; causing the ticket machine todispense, based on the dispense command, a ticket having a scratchingarea; receiving a user-provided scratching command from the applicationserver; and causing a robotic scratching device to scratch, or remove anopaque substance from, the scratching area of the ticket in accordancewith the user-provided scratching command.
 18. The non-transitorycomputer readable storage medium of claim 17, wherein the one or moreprograms further include instructions for: receiving user-providedsigning data from the application server; and causing a roboticsignature device to sign a signature area of the ticket in accordancewith the user-provided signing data.
 19. The non-transitory computerreadable storage medium of claim 17, wherein the one or more programsfurther include instructions for: obtaining, from a scanning deviceassociated with the ticket machine, an identification code of theticket; and transmitting the identification code to a ticket validationserver.
 20. The non-transitory computer readable storage medium of claim17, wherein the one or more programs further include instructions for:causing a cutting device to separate the ticket from a stream oftickets; and causing a sorting device to store the ticket in accordancewith a win status or a loss status of the ticket.